[Firebase AI] Handle empty or unknown Part data
#15262
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
WIP - needs unit test for
unary-success-empty-part.jsonAdded handling for
GenerateContentResponsevalues that contain noparts. When streaming, these are skipped since the developer can't act upon them. In unary calls, throws only if all candidates are empty since, unlike streaming, no additional responses will be returned by the backend (and therefore an empty response would be an error).This PR resolves current decoding issues when using the
gemini-2.5-flash-image-previewmodel with the Gemini Developer API, as well as hardening the decoding against malformed responses that were being returned by Vertex AI (now fixed in the backend).#no-changelog